PrizmDoc v12.0 - November 15, 2016
Configuring Log File Locations

The PrizmDoc Server are made up of several different processes, each of which create and maintain their own logs. The logs are invaluable for diagnosing issues with PrizmDoc Server if they arise. If you find yourself in this situation, please see the topic How to Package Log Files for Product Support to expedite your support request.

The directory where log files are written can be set by the logging.directory property in the central configuration file.

Example
Copy Code
logging.directory: /usr/share/prizm/logs
The following configuration properties have been deprecated and will be removed in a future release. Alter these properties only if not using the central configuration file.

If you are using legacy configuration, each logging process has a default log file path that you can change if needed. This section will discuss each process one by one and explain how to configure where log files are written.

This section contains the following information:

Watchdog

The Watchdog uses the following default log file paths:

The Watchdog will only keep up to 7 days of log files. To change where the Watchdog log files are written:

  1. Open the watchdog config file:
  1. In the paths section, change the app_log_dir property to the path of a valid directory. Both relative and absolute path are supported but a forward slash should always be used as the directory separator, even on Windows. A relative directory will be relative to the PrizmDoc Server install directory, which is C:\Prizm\ on Windows and /usr/share/prizm on Linux.
Example
Copy Code
"paths": {
      ...
        "app_log_dir": [ "C:/some/custom/path" ],
      ...
},

Entry Points

The Server and Cloud Entry Points uses the following default log file paths:

The Entry Points will only keep up to 7 days of log files. To change where the Entry Points log files are written:

  1. Open the config file:
  1. Change the logFileName property so that the directory part of the existing path is the value you choose. It is recommended that you leave the filename portion of the path as the default value. The new log file directory must be valid and exist.
Example
Copy Code
"logging": {
   "logFilePath": "%ALLUSERSPROFILE%/Accusoft/Prizm/Logs/plb.log",
   "level": "info",
   "count": 7,
   "period": "1d"
},

PCCIS

The PCCIS service uses the following default log file paths:

The PCCIS service will only keep up to 7 days of log files. To change where the PCCIS service log file are written:

  1. Open the PCCIS config file:
  1. In the target element, change the fileName property so that the directory part of the existing path is the value you choose. It is recommended that you leave the filename portion of the path as the default value.
  2. In the target element, change the archiveFileName property so that the directory part of the existing path is the value you choose. It is recommended that you leave the filename portion of the path as the default value.
Example
Copy Code
<target … fileName="C:/some/custom/path/ImagingServices.log"  archiveFileName="C:/some/custom/path/ImagingServices-{#}.log" … />

Legacy Log Path Configuration Options

Raster Conversion Service, PDF Conversion Service and AutoRedactionService Log Locations can no longer be updated in those respective Configuration files. When using Central Configuration log locations, they are set via the logging.directory parameter. If you choose to bypass the Central Configuration, these values would be set in the watchdog.config:

 

 


©2016. Accusoft Corporation. All Rights Reserved.

Send Feedback